Skip to content

docs: document the commit message convention (closes #94) - #218

Open
dchaudhari7177 wants to merge 1 commit into
stellar-compliance-kit:mainfrom
dchaudhari7177:docs/commit-conventions
Open

docs: document the commit message convention (closes #94)#218
dchaudhari7177 wants to merge 1 commit into
stellar-compliance-kit:mainfrom
dchaudhari7177:docs/commit-conventions

Conversation

@dchaudhari7177

Copy link
Copy Markdown

Closes #94.

CONTRIBUTING.md didn't specify a commit style. Adds a Commit messages section documenting Conventional Commits, with the type list, the workspace names as the scope vocabulary, subject-line rules, and four worked examples.

Described, not invented

I took the convention from the repo's own history rather than picking one:

  • the single non-merge commit on main is fix(sep10-auth): restore revocation/logger docs and exports dropped by PR #195's merge
  • merged branches consistently use feat/, fix/, docs/, ci/, chore/, test/ prefixes

So this documents what contributors are already doing, which should make it uncontroversial to enforce in review.

On commitlint

The issue said "consider wiring commitlint in CI". I've documented it as not currently wired, with a note on the natural setup (@commitlint/config-conventional + a commit-msg hook) if you want it later.

I deliberately didn't add it in this PR: it's a new dev dependency plus a CI step that would start failing PRs on message format, which feels like a maintainer call rather than something to slip into a docs change. Say the word and I'll open a follow-up that wires it.

Docs-only change.

🤖 Generated with Claude Code

…ce-kit#94)

CONTRIBUTING did not specify a commit style. Documents the Conventional
Commits format the repo already follows in practice, with the workspace names
as the scope vocabulary and worked examples.

The convention is described from the existing history rather than invented:
the one non-merge commit on main is "fix(sep10-auth): restore revocation/logger
docs...", and merged branches consistently use feat/, fix/, docs/, ci/, chore/
and test/ prefixes.

commitlint is noted as not currently wired, with the natural setup if it is
added later, so the section does not imply a check that does not exist.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a CONTRIBUTING section on commit message conventions

2 participants